@smithy/types
Usage
This package is mostly used internally by generated clients.
Some public components have independent applications.
Scenario: Removing | undefined
from input and output structures
Generated shapes' members are unioned with undefined
for
input shapes, and are ?
(optional) for output shapes.
- for inputs, this defers the validation to the service.
- for outputs, this strongly suggests that you should runtime-check the output data.
If you would like to skip these steps, use the AssertiveClient
or
UncheckedClient
type helpers.
Using AWS S3 as an example:
import { S3 } from "@aws-sdk/client-s3";
import type { AssertiveClient, UncheckedClient } from "@smithy/types";
const s3a = new S3({}) as AssertiveClient<S3>;
const s3b = new S3({}) as UncheckedClient<S3>;
const get = await s3a.getObject({
Bucket: "",
Key: "",
});
const body = await (
await s3b.getObject({
Bucket: "",
Key: "",
})
).Body.transformToString();
Scenario: Narrowing a smithy-typescript generated client's output payload blob types
This is mostly relevant to operations with streaming bodies such as within
the S3Client in the AWS SDK for JavaScript v3.
Because blob payload types are platform dependent, you may wish to indicate in your application that a client is running in a specific
environment. This narrows the blob payload types.
import { GetObjectCommand, S3Client } from "@aws-sdk/client-s3";
import type { NodeJsClient, SdkStream, StreamingBlobPayloadOutputTypes } from "@smithy/types";
import type { IncomingMessage } from "node:http";
const s3Default = new S3Client({});
const s3NarrowType = new S3Client({}) as NodeJsClient<S3Client>;
const body1: StreamingBlobPayloadOutputTypes = (await s3Default.send(new GetObjectCommand({ Key: "", Bucket: "" })))
.Body!;
const body2: SdkStream<IncomingMessage> = (await s3NarrowType.send(new GetObjectCommand({ Key: "", Bucket: "" })))
.Body!;